Fix missing or generic image alt text in blog/ posts #1121 #1123
Conversation
…ility and SEO - Updated generic alt text in blog posts to descriptive ones - Replaced 'GitHub' alt text in docs with specific image descriptions - Improved accessibility by providing meaningful alt attributes - Enhanced SEO through descriptive image content Closes recodehive#1121
|
@Gupta-02 is attempting to deploy a commit to the recode Team on Vercel. A member of the Team first needs to authorize it. |
|
Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs. In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊 Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv. We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰 🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨ 📚Your perks for contribution to this community 👇🏻
If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊 |
github-actions
bot
added
hacktoberfest-accepted
recode
|
✅ Synchronized metadata from Issue #1121:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Thanks sir : ) |
2 participants
Fixes #1121
Several blog posts and documentation pages included images without descriptive alt attributes. Updated them to be descriptive and meaningful for better accessibility and SEO. This ensures compliance with WCAG guidelines and improves the user experience for screen readers and search engines.
Why it matters: Accessibility and SEO.
Acceptance criteria:
Identify images in blog/ or docs/ with empty/placeholder alt text
Update the markdown to include descriptive alt="..." attributes
Include a short explanation of why the chosen text is descriptive in PR
Type of Change
Bug fix (non-breaking change that fixes an issue)
New feature (e.g., new page, component, or functionality)
UI/UX improvement (design, layout, or styling updates)
Performance optimization (e.g., code splitting, caching)
Documentation update (README, contribution guidelines, etc.)
Other (please specify): Accessibility improvement
Changes Made
Blog Posts (8 files updated):
index.md: Changed generic "UI-UX Design impact in future" to "Infographic showing career growth and opportunities in UI/UX design"
index.md: Updated to "Illustration of human qualities that AI cannot replace in UX design"
index.md: Replaced "img1" with "Flowchart illustrating the user research process in UX design"
index.md: Corrected to "Promotional banner for GitHub Copilot Coding Agent feedback rewards"
Other blog files maintained their already descriptive alt text
Documentation (14 files updated):
setup-environment.md: Updated 6 images from "GitHub" to specific Git installation screenshots
docs/sql/SQL-joins/.md: Changed "GitHub" to descriptive SQL join diagram/animation descriptions
docs/Google-Student-Ambassador/.mdx: Replaced "GitHub" with detailed program-related image descriptions
docs/sql/SQL-Advance/*.md: Updated to specific database concept illustrations
Why the chosen alt text is descriptive:
Each updated alt attribute now provides a clear, specific description of the image's content and purpose, rather than generic placeholders. This ensures:
Accessibility: Screen readers can convey meaningful information to visually impaired users
SEO: Search engines can better index and understand page content
User Experience: Users with slow connections or disabled images get context about what's missing
Dependencies
No new dependencies required
No version updates needed
No additional configurations required
Checklist
My code follows the style guidelines of this project.
I have tested my changes across major browsers and devices (markdown changes, no visual impact)
My changes do not generate new console warnings or errors.
I ran npm run build and attached screenshot(s) in this PR. (Not applicable for markdown-only changes)
This is already assigned Issue to me, not an unassigned issue.